Email-Based Data Transfer and Synchronization

ABSTRACT

A database system provides email synchronization a table. The database system receives a request to synchronize data to a data table using an email. The database system generates a table email address for the data table. The table email address is a new email address associated with the data table. The database system receives an email addressed to the table email address. The email comprises a data file including one or more records, each record of the one or more records comprising a respective record identifier. The database system maps the one or more records to the data table using the respective record identifiers. The database system updates the data table using the mapped one or more records.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.63/238,010, filed Aug. 27, 2021, which is incorporated by reference.

BACKGROUND 1. Technical Field

The subject matter described relates generally to databases and, inparticular, to techniques for synchronizing data to a table via email.

2. Background Information

Enterprises and other entities often provide different users with accesspermission to different subsets of the data available to the entity. Asa result, entities typically maintain multiple databases that includepartially overlapping data. Maintaining consistency between theoverlapping portions can be a time-consuming and error prone task. Forexample, if a human is responsible for entering new data into multipledatabases, typographical and other errors may lead to discrepanciesbetween different versions of the data. One approach to addressing thisproblem is to store the data in a single database and control whichusers have access to which records but maintaining the accesspermissions in this scenario is also a time-consuming process. Thisprocess is also subject to error. For example, human error in updatingpermissions may reveal confidential data to users who are not authorizedto access it.

Maintaining a database that includes data from several sources can beespecially time-consuming and error prone. When an attribute in thedatabase includes data taken from multiple sources, data loss can occurwhen different sources have different data types or different labels forthe attribute.

Sometimes, moving data from an internal system or an external system toa third-party server can be difficult. For example, moving data from aninternal system to a third-party server can involve using an applicationprogramming interface (API), which can be difficult to integrate withthe internal system, especially if the user lacks technical knowledge.Also, moving data from an external system to a third-party server notaffiliated with the external system can be difficult, for example, ifthe external system is not integrated with the third-party server.

SUMMARY

The above and other problems may be addressed by, and the disclosedembodiments include a database system that provides automaticsynchronization from one or more databases to a table. The synchronizedportion of each source database table may be periodically (e.g., onceevery five minutes, once an hour, etc.) imported into a correspondingportion of a destination database table. In an embodiment, for eachsynchronized field in the table with data from multiple sourcedatabases, one of the source databases is set as a primary source, whichdetermines the data type and field configuration of the field, and datafrom secondary sources are cast to the data type established by theprimary source and represented using the primary source's fieldconfiguration.

The source database table may also include data that is not synchronizedwith the destination database table. Similarly, the destination databasetable may be enriched with data that is not included in the sourcedatabase table.

In an embodiment, the database system receives a request to add data toor update data in the table via email. The database system generates anemail address for the table. The database system receives a data fileincluding data for the destination database table. For example, the datafile may be a comma-separated values (CSV) file. The data file includes,for each record in the data file, a record identifier. The databasesystem maps the records of the data file to the destination databasetable using the respective record identifiers. The database systemupdates the destination data table using the mapped records.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked computing environment suitablefor providing partially synchronized database tables, according to oneembodiment.

FIG. 2 is a block diagram of the server of FIG. 1 , according to anembodiment.

FIG. 3 is a block diagram of the bases data store of FIG. 2 , accordingto one embodiment.

FIG. 4 illustrates multisource synchronization of three tables of threedatabases in the bases data store 210, according to one embodiment.

FIG. 5 is a flowchart of a method for partially synchronizing databasetables, according to one embodiment.

FIG. 6 illustrates a method for multisource synchronizing databasetables, according to one embodiment.

FIG. 7 illustrates a method for email synchronizing a database table,according to one embodiment.

FIG. 8 illustrates a user interface for email synchronization to adatabase table, according to one embodiment.

FIG. 9 illustrates a user interface to visualize a database error,according to one embodiment.

FIG. 10 is a block diagram illustrating an example of a computersuitable for use in the networked computing environment of FIG. 1 ,according to one embodiment.

DETAILED DESCRIPTION

The figures and the following description describe certain embodimentsby way of illustration only. One skilled in the art will readilyrecognize from the following description that alternative embodiments ofthe structures and methods may be employed without departing from theprinciples described. Wherever practicable, similar or like referencenumbers are used in the figures to indicate similar or likefunctionality. Where elements share a common numeral followed by adifferent letter, this indicates the elements are similar or identical.A reference to the numeral alone generally refers to any one or anycombination of such elements, unless the context indicates otherwise.

The techniques described provide for email-based data synchronization,whether local or external, such that the data in a synchronized datatable is consistent and up to date. Synchronized data tables can be usedto allow various groups of users to manage and evolve their databasesand workflows independently, while still being able to collaborate onshared data tables where data from various sources is aggregated.Furthermore, this may provide data synchronization with fewertranscription errors than existing approaches. Email synchronizationallows data to be imported from a remote location and using standardizedformats.

The described techniques may also provide for increased data security.For example, email synchronization can be configured to restrictsynchronization rights to particular domains or email addresses,allowing straightforward data synchronization without exposing thedatabase to external threats. A synchronized data table can be used toexpose particular up-to-date data to external users, e.g., fromdifferent organizations, with tight control over the schedule on whichthe data updates, and the ability to revoke data sharing, thus balancingcollaboration and security in interorganizational sharing.

These and other benefits can be recognized in view of the presentdisclosure.

Example Systems

FIG. 1 illustrates one embodiment of a networked computing environment100 suitable for providing partially synchronized database tables. Inthe embodiment shown, the networked computing environment 100 includes aserver 110, an external server 115, a first client device 140A, a secondclient device 140B, and a client server 145, all connected via a network170. Although two client devices 140 are shown, the networked computingenvironment 100 can include any number of client devices 140. Similarly,although one external server 115 is shown, the networked computingenvironment 100 can include any number of external servers 115, or anynumber of client servers 145. In other embodiments, the networkedcomputing environment 100 includes different or additional elements. Inaddition, the functions described herein may be distributed among theelements in a different manner than described.

The server 110 hosts multiple databases and performs synchronizationbetween databases, such as with a cross-base synchronize function or anemail-based synchronize function. The cross-base synchronize functioncopies data from a shared source view to a target table. Data may becopied in one direction during a synchronization.

When a synchronization completes, the target table contains all of therows in the source view and cell data for all columns (alternatively,“fields”) selected to be synchronized. In one embodiment, only data(rows and columns) that are explicitly or implicitly set as ‘visible’ inthe shared view can be copied. Users may determine what data isavailable to synchronize (and in what form) using a shared viewinterface (e.g., to designate one or more rows or columns as visible ornot visible). As described in further detail below, a user cansynchronize some or all data from one or more sources to a target table,and one or more of the sources can be external to the server 110, e.g.,may be hosted by an external server 115. Further, a user can synchronizedata to a target table using an email.

In an embodiment, data in the target table matches the format of thedata in the shared view interface. For example, if linked records arerendered as text in shared views, they also render as text in the targettable. Formulas may render as their result type and look like anon-formula field. As a consequence of this design, synchronization doesnot differentiate between data being deleted from the source table orsimply being hidden from the shared view. As described in further detailbelow, matching data from source to target table can follow analternative technique.

The following table illustrates the mapping between source and targetdata types for one embodiment:

Source type Target type Number/date/single-line text/long Identical typeand configuration (e.g. number/date text/rich text/select/multi-selectformatting, select color and order) Foreign key TextCollaborator/Multi-collaborator Text Lookups As the looked-up type (sosynchronizing a lookup of a foreign key will result in text)Formulas/Rollups As the result type Button fields ‘Open URL’ type buttonfields will be synchronized as URL field Attachments As-is

A synchronized target table mirrors the contents of its source view butcan contain additional unsynchronized columns to enrich the synchronizeddata. For example, one might collect T-shirt sizes for all employees bysynchronizing into the target table a list of employees and then addingan unsynchronized ‘T-shirt size’ column, where each employee enrichesthe target table by entering their T-shirt size to a respective row atthe ‘T-shirt size’ column.

In an embodiment, users of the target table are not allowed to create ordestroy records in the synchronized portion of the table, nor to changecell values or column type and type options for any synchronized column,but they can make changes to non-synchronized columns. In someembodiments, users of the target table may change the names anddescriptions for synchronized columns, which does not impact the sourcetable (i.e., source view) but changes how the synchronized data isdisplayed in the target table (e.g., a column in the target table has adifferent name than the corresponding column in the source table).

Various embodiments of the server 110 are described in greater detailbelow, with reference to FIG. 2 .

The client devices 140 are computing devices with which users can accessand edit the databases managed by the server 110. Example client devicesinclude desktop computers, laptop computers, smartphones, tablets, etc.The client devices 140 may enable users to interact with the databasesvia a user interface accessed via a browser, a dedicated softwareapplication executing on the client devices, or any other suitablesoftware.

The external server 115 is a server, which may be associated with adifferent entity than the server 110. For example, server 110 isassociated with a first organization, and server 115 is associated witha second organization. The external server 115 may be, for example, aSALESFORCE server, a JIRA server, a GOOGLE CALENDAR server, or a BOXserver. Users of client devices 140 can synchronize data from sourcetables in databases hosted at the external server 115 to target tablesat the server 110. This can involve the user providing credentialinformation, which the server 110 uses to connect to the external server115.

The server 110 can synchronize data from the external server 115 to atarget table in a database of the server 110. In one embodiment, theserver 110 stores a tabular data mapping to translate data from theexternal server 115 to a usable format for server 110 databases. Theserver 110 may store a different tabular data mapping for each ofmultiple external servers 115 to facilitate data transfer to the targettable. For example, the server 110 may store a first tabular datamapping for SALESFORCE reports that uses a SALESFORCE applicationprogramming interface (API), a second tabular data mapping for JIRAissue filters that uses a JIRA API, and a third tabular data mapping forGOOGLE CALENDAR events that uses a GOOGLE CALENDAR API. Using the API ofan external server 115, the server 110 can request and receivesynchronized data for a target table. For example, the server 110 maysend a query to the external server 115 using a respective API function,where the query specifies the data to be synchronized to the targettable, and then the server 110 receives, via a different API function,query results including the synchronized data from the external server115. The server 110 identifies an external server 115, fetches therespective tabular datamapping, and uses the respective tabular datamapping to synchronize data from the external server 115 (e.g., to atarget table).

The client server 145 is a server that is associated with (e.g.,deployed by) one or more client devices 140 or an organizationassociated with the one or more client devices 140. For example, theorganization may be a business that provides a service via the network170 and the client server 145 is a database including data of thebusiness. One or more client devices 140 have administrative controlover the client server 145, e.g., can adjust its content and settings.One or more client devices 145 can perform one or more operationsinvolving the client server 145, such as querying a database at theclient server 145 for data or submitting data to the client server 145for storage at the database at the client server 145. As a particularexample, a client device 140 of an engineer from the aforementionedexample business may apply updated infrastructural program code to theclient server 145 to integrate its database with a new service, or aclient device 140 of a businessperson may submit business data to theclient server 145 for storage at its database.

The network 170 provides the communication channels via which the otherelements of the networked computing environment 100 communicate. Thenetwork 170 can include any combination of local area and wide areanetworks, using wired or wireless communication systems. In oneembodiment, the network 170 uses standard communications technologiesand protocols. For example, the network 170 can include communicationlinks using technologies such as Ethernet, 802.11, worldwideinteroperability for microwave access (WiMAX), 3G, 4G, 5G, code divisionmultiple access (CDMA), digital subscriber line (DSL), etc. Examples ofnetworking protocols used for communicating via the network 170 includemultiprotocol label switching (MPLS), transmission controlprotocol/Internet protocol (TCP/IP), hypertext transport protocol(HTTP), simple mail transfer protocol (SMTP), and file transfer protocol(FTP). Data exchanged over the network 170 may be represented using anysuitable format, such as hypertext markup language (HTML) or extensiblemarkup language (XML). In some embodiments, all or some of thecommunication links of the network 170 may be encrypted using anysuitable technique or techniques.

Embodiments of various techniques of the networked computing environment100 will now be described. Alternative techniques may be employedwithout departing from the principles set forth herein.

A user of client device 140A can interface with the server 110 to createa synchronized target table according to one or more techniques,depending upon the embodiment. The user interface may be exposed by theserver 110 or client device 140A. In one embodiment, the user receives alink to a shared view (e.g., from an administrator of the databaseincluding the shared view). The user provides an instruction the server110 to use the link to initiate a synchronization, either with a newtable or an existing table. The server 110 sets up the requestedsynchronization between the shared view and the selected table. In oneembodiment, the user selects a widget of a user interface exposed by theserver 110 that displays a shared view to create a new synchronizedtable using the shared view.

In an embodiment, the link to the shared view may be temporary, e.g.,only useable once, or for a finite period of time, such as 24 hours.Thereafter, the source table may be identified by a source tableidentifier. In this manner, the source table can be secured, such thatif the user ends synchronization to the target table, the link cannot beused to inappropriately gain access the source table. In an embodiment,a user that shares a like to a shared view to another user may revokeaccess to the shared view from the other user.

In one embodiment, the user has access permission to the source tableand the target table. The user can create a new shared view or enablesynchronization of an already-existing shared view. The user can thenproceed with one of the above techniques. Alternatively, the user cannavigate to a user interface that displays the target table and select awidget to expose a list of potential source tables. The user can selectthe shared view to use it as a source table. In various embodiments, theuser can set a table (e.g., for which the user has access permission) asable to be synchronized (i.e., can be used as a source table) or not. Invarious embodiments, the user can designate some or all of the rows orcolumns in the table as able to be synchronized or not.

In an embodiment, the user can restrict access to the table such that itis password protected. Additionally or alternatively, the user canrestrict access to the table such that only users associated withspecified email addresses or email domains can access the table.

In one embodiment, if a source table is password-protected, the userinitiating synchronization to a target table is prompted to correctlyenter the password to the source table in order to set up thesynchronization. Once the password has been entered, synchronization mayoperate automatically, indefinitely, or for a predetermined time period(e.g., one month or one year) without requiring password reentry. If thepassword changes, or if a password is added to a previously unprotectedsource table, the synchronization stops working until authenticated orreauthenticated. In an embodiment, the user can revoke accesstemporarily or permanently.

In one embodiment, if a source table is email domain-protected, the userinitiating the synchronization needs to have a verified email with apermissioned domain in order to set up the synchronization. If theinitiating user's email address with the permissioned domain isdeactivated, suspended, or otherwise made inactive, the synchronizationmay cease to operate. Alternatively, a synchronization may remainoperational as long as any user of the target table has an email addresswith a permissioned domain.

In an embodiment, the user can add one or more external source tables toa synchronized table by selecting an external source widget in the userinterface. The user can then pick another source type (e.g. AIRTABLE,SALESFORCE, or JIRA.), select the source table within that type, andthen map the fields from the new source table to the fields in theexisting table. For each column in the target table, the user interfacedisplays a list of columns in the source table, from which the user canselect one column in the source table to associate with the column inthe target table (e.g., such that data from the column in the sourcetable is synchronized to the respective column in the target table).

In some embodiments, when adding a new source, the server 110 tries tomatch column names to existing column names, as described in furtherdetail below. For columns that cannot be matched, the default option maybe to synchronize that data to a new column in the target table instead.The user can change any mappings or opt to synchronize any source columnto a new synchronized column.

In an embodiment, an option to select all columns is not available whenthere are multiple synchronization sources. When the user adds a newsource table, if an existing source table is configured to synchronizeall columns, that source table is changed to synchronize specificcolumns only. The user can use the user interface to alter the fieldmapping by selecting a widget to change mappings. In an embodiment,synchronized target tables that do not synchronize from multiple sourcetables do not include a field mapping. Rather, the target table uses thefields of the source synchronization table.

In an embodiment, after a synchronization is initiated for a targettable from a source table, for every source table field, the user canselect a new target table field in a dropdown of the user interface tochange the target table field associated with the source table field.

Alternatively or additionally, the user can uncheck a field in the userinterface to stop synchronizing data from this source table to themapped target table field, where, if this source table was the primarysource, the synchronized target table column will be destroyed.

Alternatively or additionally, the user can synchronize to a new targettable field, where if the source table field was previously mapped to atarget table field and the source table was the primary source, thesynchronized field may be destroyed, and the data mapped to a new fieldinstead. If the source table was not the primary source, the data may bemapped to a new field. If the source table field was previouslyunmapped, the data in the source table field may be mapped to a newtarget table field.

In an embodiment, the user can reconfigure, using the user interface, aselection of one or more columns to synchronize to a target table from asource table. Alternatively or additionally, the user can reconfigure asynchronization frequency with which the target table synchronizes tothe source table.

Alternatively or additionally, the user can reconfigure whether deletedor hidden rows in the source table are deleted in the target table,where if the user does not choose to delete rows, rows will remain inthe target table even after they are deleted in the source table (theserows can be removed by the user).

Alternatively or additionally, the user can remove a source table, whichremoves all rows associated with the source table. Alternatively oradditionally, the user can turn off synchronization functionality forthe target table, which converts the target table into a normal (e.g.,unsynchronized) data table.

Alternatively or additionally, the user can undo a reconfiguration,which restores the previous set of selected fields, the old synchronizefrequency, the old row deletion setting, and so on; however, theavailability of the fields and the cell values in the fields remains upto date, since the values come from the source table, and as such theyare not reverted to their data from before the reconfiguration.

Alternatively or additionally, the user can trigger a manualsynchronization by clicking a widget of the user interface to initiate asynchronization. The user can do this even when the table is configuredto synchronize automatically. This allows the user to synchronize thetarget table without having to wait for the next scheduledsynchronization.

In an embodiment, removing all synchronizations to source tables from atarget table causes the target table to convert into a normal table thatis not synchronized. No data is removed from the target table, but nofuture changes to source tables are synchronized to the target table.Depending upon the embodiment, this action may not be able to be undone.

In one embodiment, a user can add a button field to the target table andset label text and a color of their choice, where the button links tothe source table. When another user clicks this button, the source tableopens to the corresponding record in the source table in a new tab ofthe user interface (if the other user has access permission). Foranother user that has access to both the source table and target table,the other user can view unsynchronized fields of that source table ormake changes to the source table. If the user has configured the targettable to not delete rows that are hidden or deleted in the source table,the button may be unable to be selected or visually distinguished whenthe source record is hidden or deleted. Depending upon the embodiment,formulas or view filters may consume the output of the button field,e.g., the output of the button field can be a link of the source table'srecord, or null if the source table's record is no longer available.

In one embodiment, if a target table is duplicated, the duplicate tablehas the same configuration as the original target table. If the userdeletes a target table, then restores it, the target table may regainits original configuration from before its deletion.

In an embodiment, the user can change one or more column names ordescriptions of the synchronized portion of the target table. This canbe used to rename columns to be more appropriate for the target table,for example. In an embodiment, when a user hovers over a column icon inthe user interface, they can see the name of the respective source tablecolumn (if the target column has a different name). Depending upon theembodiment, the user may or may not be able to add a row, destroy a row,reconfigure a synchronized column, or edit a cell in a synchronizedcolumn.

The following table illustrates a correspondence of actions taken upon asource table and responsive changes in a target table subsequent to asynchronization, according to one embodiment:

Source table action Target table behavior on next synchronizationDestroy/hide column Destroy column Undestroy/unhide column Undestroycolumn if possible/else create a new column. Add column If ‘synchronizeall fields’ is enabled, add column Add row Row will be added to thetarget table Destroy/hide row If ‘synchronize deletions’ is enabled:destroy row Otherwise: the “open source record” button gets disabledChange cell values Change cell values (based on type conversion) Changefilters The set of visible rows will be synchronized Reorder rows Noimpact Change column configuration to Destroy column unsupportedtype/configuration Change column configuration to Change column config(based on type conversion) supported type/configuration Disablesynchronizing Synchronizing stops working Re-enable synchronizingSynchronizing resumes Delete view Synchronizing stops working Undestroyview Synchronizing resumes Change share URL Synchronizing stops,requires re-authentication Add/change shared view password Synchronizingstops, requires re-authentication Add domain restriction that the userSynchronizing stops, requires re-authentication by a does not satisfyuser in the target table with the appropriate domain

In an embodiment, synchronization may be two-directional between twotables, where each table acts as a source table and a target table, andsynchronized data added to either table is propagated to the other upona subsequent synchronization.

In an embodiment, a user can generate a view-only link to send toanother user, which the other user can use to view the target table only(i.e., the other user cannot edit the target table). Alternatively oradditionally, the user can set a user (e.g., by identifier or emailaddress) or a domain as view-only, where the respective one or moreusers can view but not edit the target table.

In an embodiment, if a field mapping from one source table column to onetarget table column is removed (e.g., by the user), then added back, theserver 110 attempts to restore the same column (thus restoring anylookups that reference that column, or calendars that use it as the datefield, etc.). If the server 110 cannot restore the original column, anew column is created instead.

In an embodiment, if a field of a source table was previouslysynchronized but has since been made unable to be synchronized (e.g., byan administrator of the source table), the user interface may displaythe source table column as visually distinct (e.g., faded out or analternative color) than other source table columns. The user can togglewhether to synchronize currently unavailable fields, though they do notappear when the user toggles them on. Only fields that are currentlyavailable from the source table, along with any currently selected butunavailable fields, appear in the field list.

FIG. 2 illustrates one embodiment of the server 110. In the embodimentshown, the server 110 includes a bases data store 210, a data accessmodule 220, a data update module 230, a data synchronize module 240, anemail synchronize module 245, and a mapping data store 250. In otherembodiments, the server 110 includes different or additional elements.In addition, the functions may be distributed among the elements in adifferent manner than described.

The bases data store 210 includes one or more computer-readable mediathat store the one or more databases managed by the server 110. Althoughthe bases data store 210 is shown as a single element within the server110 for convenience, the bases data store 210 may be distributed acrossmultiple computing devices (e.g., as a distributed database). Similarly,individual databases may be hosted by client devices 140 (or othercomputing devices) with the server 110 managing synchronization betweendatabases but not storing the databases themselves.

The data access module 220 provides a mechanism for users to access datain one or more databases. In one embodiment, the data access module 220receives a request from a client device 140 indicating an identifier ofthe requesting user (e.g., a username or user identifier) and data froma specified table in a specified database that the user wishes to view.The data access module 220 determines whether the user has permission toaccess the requested data and, if so, provides it to the client device140 from which the request was received for display to the user.

The data update module 230 provides a mechanism for creators and theircollaborators to edit data in and add data to databases. In oneembodiment, the data update module 230 receives a request from a clientdevice 140 indicating an identifier of the requesting user and data tobe added to or amended into a specified table in a specified database.The data update module 230 determines whether the requesting user haspermission to edit the specified table and, if so, updates the specifiedtable in the bases data store 210 as requested.

The data synchronize module 240 updates some or all portions of targettables to synchronize them with the corresponding source table (ortables). In one embodiment, the data synchronize module 240 periodically(e.g., for a length of time ranging from one second to one hour, such asevery five minutes, every hour, etc.) checks the one or more sourcetables and, if there is updated data available, imports it into thecorresponding one or more target tables (e.g., updates records in thetarget table with respective records from the source table).Additionally or alternatively, users of a target table may force amanual synchronization to one or more source tables (e.g., by selectinga control in the user interface).

The mapping data store 250 can include one or more computer-readablemedia that store tabular data mappings for one or more external servers115. Although the mapping data store 250 is shown as a single elementwithin the server 110 for convenience, the mapping data store 250 may bedistributed across multiple computing devices (e.g., as a distributeddatabase).

A user with suitable permissions to a pair of databases may select asubset of the data in a table in one database (e.g., a source table) tosynchronize with a corresponding table in a second database (e.g., atarget table). Thus, the two tables are referred to as partiallysynchronized, as only a subset of the rows or columns from the sourcetable are used to populate the target table. However, it should be notedthat complete synchronization is also possible, meaning all of thesource table is synchronized with the destination table, and thedestination table has not been enriched with any additional data (thoughit may be, depending upon the embodiment). As described below, a usercan synchronize some or all data from multiple source databases to onetable at one database.

The email synchronize module 245 performs operations for emailsynchronization of data to a data table. The email synchronize module245 receives requests to synchronize data via email to a data table andsets up an email address for the data table, as described in greaterdetail below. In one embodiment, the email synchronize module 245receives an email that includes a data file for synchronization to thedata table and can verify the email is from a legitimate sender (e.g.,is associated with an organization that is associated with the datatable). The email synchronize module 245 maps records of the data fileto records in the data table and updates the data table using the mappedrecords.

The email synchronize module 245 can also maintain a sync history, whichtracks changes to records in the data table over time, e.g., after eachsynchronization of data to the data table. In some embodiments, e.g.,where data is synchronized to the data table using email synchronizationand also an alternative technique (e.g., across-base sync), the synchistory tracks changes to records in the data table for one or bothtechniques, and may include indicators of from which source a change toa record originated. Changes to records over time can be tracked usingrecord identifiers. Each record has a record identifier thatdifferentiates the record from other records, and can be used toidentify the same record at different times (e.g., after differentsynchronizations and having different values).

Depending upon the embodiment, the email synchronize module 245 receivesdata files via email from a client device 145, an external server 115,or a client server 145. For example, a data analyst at a businessassociated with a data table at the server 110 may email a data file tothe server 110, or a client server 145 of the business (e.g., an orderhistory database) may email a data file to the server 110, or anexternal server 115 associated with the business (e.g., a partnerorganization or a service employed by the business) may email a datafile to the server 110. In an embodiment, the server 110 onlysynchronizes data files from emails received from email addressesauthorized to send data files, e.g., according to a list of authorizedemails as set by an administrator, or from a particular domain (such asa domain of the organization associated with the data table).

Each record in the data table and each data file has a recordidentifier, which may be one or more attributes of the record. Therecord identifier may be selected by a client device 140, e.g., a clientdevice 140 sends a selection of one attribute of a set of attributescommon to records in the data table, which is received by the server110, and thereafter used as the record identifier. For example, a clientdevice 145 may indicate that a “transaction identifier” attribute is tobe used as the record identifier. Alternatively, the server 110 maydetermine the record identifier. For example, the server 110 may checkthe data table to identify one or more attributes such that each recordin the data table has a different value for the attribute. The server110 sets as the record identifier one of the one or more attributes thatmatches this criteria (e.g., a first-identified of the attributes). Inan embodiment, the server 110 identifies a minimal set of one or moreattributes such that each record in the data table has a differentrecord identifier. As a particular example, the server 110 may determinethat a “transaction identifier” attribute of each record in the datatable is different from the others, and therefore uses the transactionidentifier attribute as the record identifier. Alternatively, the server110 may determine that multiple records share a transaction identifier,but that a combination of “year,” “month,” “day,” and “time” attributesdifferentiates each record in the table from the rest, and thereforeuses the combination of those four attributes as the record identifier.

Record identifiers can be used to map records from the data file to thedata table even if the records include attributes with different namesor orders of attributes and the records themselves are in a differentorder in the data file than the data table. For example, a record in thedata table may include a “date” attribute and then a “order number”attribute, while a record in the data file may include a “number”attribute and then an “order date” attribute. Depending upon theembodiment, the server 110 or a user (e.g., via instructions receivedfrom a client device 145) maps the attributes of the data table toattributes of the data file (e.g., by matching similar attribute namesor data types). The record identifier can be used to map a specificrecord in the data file to a specific record in the data table, even ifthey have nearly completely different data values for their respectiveattributes, and even if they have different ordinal positions in therespective data representation, because the shared record identifier canbe used to match the two specific records.

In some embodiments, records can have multiple record identifiers, e.g.,one record identifier for data files from one source and a second recordidentifier for data files from a second source.

In some embodiments, if the server 110 encounters one or more errorswhen performing an email synchronization, the server 110 may send to aclient device 145 an alert that the error occurred. The alert mayinclude a copy of the data file that was being synchronized (e.g., foruse by the client device 145 for determining the cause of the error).Depending upon the embodiment, the server 110 may handle certainexceptions, such as bad file type, bad encoding, non-unique recordidentifiers (e.g., the server 110 could not identify a set of attributesthat differentiates each record in the data table), unreadable rowvalues, too many files, or that the server is down.

FIG. 3 illustrates the partial synchronization of two tables of twodatabases in the bases data store 210, according to one embodiment. Inthe embodiment shown, the bases data store 210 includes base one 310 andbase two 320. In practice, the bases data store 210 will likely includemany more (e.g., hundreds, thousands, or even millions of) bases. Baseone 310 includes table one 312, which has a synchronized portion 315 andan unsynchronized portion 317. Base two 320 includes table two 322,which includes a synchronized portion 325 (which mirrors thesynchronized portion 315 of table one 312 except for any differencesthat arose since the previous synchronization operation) and an enrichedportion 329. The enriched portion 329 may include data added by users ofbase two 320, data synchronized from a third table, or both.

The third table in such a case may either be another table in base one310 or from a third base (not shown). It should be noted that table two322 is not limited to receiving synchronized data from just two tables.In theory, table two 322 may receive synchronized data from an unlimitednumber of other tables, limited only by computational and memoryrequirements. Similarly, synchronization is not limited to a singlegeneration. Table two 322 may serve as a source table for a thirddestination table, which may in turn serve as a source table for anothertarget table, etc. Furthermore, each synchronization relationshipbetween a source table and a target table may share a different subsetof data selected from either the synchronized portion 325, the enrichedportion 329, or both.

FIG. 4 illustrates multisource synchronization of three tables of threedatabases in the bases data store 210, according to one embodiment. Inthe embodiment shown, the bases data store 210 includes base one 410A,base two 410B, base three 410C, and a field name data store 420. Baseone 410A includes table one 412A, which has a synchronized portion 415Aand an unsynchronized portion 417A. Base two 410B likewise includestable two 412B, which has a synchronized portion 415B and anunsynchronized portion 417B. The field name data store 420 storesmappings between potential field names that have a high likelihood ofbeing synonymous (e.g., “first name” and “given name”). The bases datastore 210 may include additional bases or tables, depending upon theembodiment.

Base three 410C includes table three 412C, which includes a synchronizedportion 425 and an enriched portion 429. The enriched portion 429 mayinclude data added by users of base two 410B, data synchronized from afourth table, or both. For example, the server 110 may receive userinput data (e.g., data that a user input to a client device 140 and sentto the server 110) specifying additional one or more rows or columns toadd to table three 410C.

In this embodiment, table three 412C includes a column 427 thatsynchronizes data from two sources, table one 412A and table two 412B.For example, column 427 includes ten records total, six received fromtable one 412A and four from table two 412B. A user administrating tablethree 412C (e.g., using a client device 140) sets table one 412A as theprimary source. Depending upon the embodiment, the primary source may beautomatically set by the server 110, e.g., based on which source isfirst synchronized to the column 427, or which source provides the mostrecords to the column 427; the automatically set primary source may beupdated by the user, in some embodiments. Source tables other than theprimary source may be considered secondary sources.

The server 110 uses the primary source to determine the data type of thecolumn 427. Data from other sources, e.g., table two 412B, is cast tothe data type of the data from the primary source in the column. Thisresolves ambiguities which may arise from synchronizing columns ofmultiple source tables with different data types to one column in atarget table.

For example, the column synchronized from table one 412A to the column427 may have a data type “text,” where the column synchronized fromtable two 412B to the column 427 may have a data type “date.” Becausetable one 412A is the primary source, the server 110 sets column 427 ashaving data type “text” and casts data from table two 412B for column427 as “text.”

The server 110 may also determine the field configuration for the column427 based on the respective field configuration of the column at theprimary source from which data is synchronized. In one embodiment, theprimary source determines whether the column in the target table isremoved when the source table's column is hidden or destroyed. Forexample, if a column of a primary source is removed from the sourcetable, the server 110 removes the respective column from the targettable, but if the corresponding column is removed from a differentsource table, only records in the target table corresponding to thedifferent source table are affected (e.g., removed). For a target tablewith a single source table, the single source table can be considered tobe the primary source for all fields.

The user also performs field mapping for synchronized fields from tableone 412A and table two 412B to table three 412C. In the field mapping,the user sets a correspondence between a column at each source to acolumn at table three 412C. The server 110 initially attempts to matchfields from sources to table three 412C according to field name, whichthe user can override via a user interface. The server 110 comparesfield names from synchronized columns of a source (e.g., table one 412A)to field names of synchronized columns in the target table (e.g., tablethree 412C) and, upon identifying a matching pair, maps the source fieldto the target field.

For example, table one 412A may include a “first name” field and a “lastname” field, table two 412B may include a “given name” field, a “middlename” field, and a “surname” field, and table three 412C may include a“first name” field and a “family name” field. The server 110 matches the“first name” field from table one 412A to the “first name” field fromtable three 412C, indicating that data from the “first name” field oftable one 412A will synchronize to the “first name” field of table three412C. The user maps the “given name” field of table two 412B to the“first name” field of table three 412C, and the “last name” field oftable one 412A and the “surname” field of table two 412B to the “familyname” field of table three 412C. As such, data from table one 412A andtable 412B will synchronize to the mapped fields in table three 412C.

In an embodiment, the server 110 auto-matches columns with synonymousfield names, as determined according to the field name data store 420.The field name data includes mappings between field names that arelikely to be synonymous. Thus, the server 110 can use the field namedata to identify columns with different but synonymous names as likelymatches. The matches can be automatically applied or presented to theuser as suggestions for verification.

Example Methods

FIG. 5 illustrates a method 500 for partially synchronizing databasetables, according to one embodiment. The steps of FIG. 5 are illustratedfrom the perspective of the server 110 performing the method 500.However, some or all of the steps may be performed by other entities orcomponents. In addition, some embodiments may perform the steps inparallel, perform the steps in different orders, or perform differentsteps.

In the embodiment shown in FIG. 5 , the method 500 begins with theserver 110 configuring 505 a periodic synchronization between a firstdatabase and a second database. This may be prompted by the server 110receiving a request to do so. The server 110 receives 510 a request toupdate a first table in a first database. The server 110 updates 520 thefirst table as requested. As part of a synchronization operation (eitherperiodic or manually triggered), the server 110 imports 530 a portion ofthe updated first table into a corresponding portion of a second tablein a second database. Depending upon the embodiment, the portion of theupdated first table imported 530 to the second table may include onlythe subset of data of the updated first table that has changed since aprevious synchronization operation, or the portion may include all datadesignated for synchronization from the first table to the second table.The server 110 also enriches 540 the second table with additional datawithout impacting the first table. As described previously, theadditional data may be imported from another table, entered by a user ofthe second database, or both.

FIG. 6 illustrates a method 600 for multisource synchronizing databasetables, according to one embodiment. The steps of FIG. 6 are illustratedfrom the perspective of the server 110 performing the method 600.However, some or all of the steps may be performed by other entities orcomponents. In addition, some embodiments may perform the steps inparallel, perform the steps in different orders, or perform differentsteps.

In the embodiment shown in FIG. 6 , the method 600 begins with theserver 110 receiving 610 a request to add a second source to a firsttable in a first database that synchronizes data from a first source.The server 110 receives 620 a designation of the second source as aprimary source. As such, data from the first source that is synchronizedto portions of the first table where data from the second source alsosyncs will be cast to the data type of the data received from the secondsource for that portion and configured according to a fieldconfiguration of the data received from the second source for thatportion. The server 110 imports 630 data from the first source and thesecond source to the first table, where data from the first source iscast to the type specified by the second source.

FIG. 7 illustrates a method 700 for email synchronizing a databasetable, according to one embodiment. The steps of FIG. 7 are illustratedfrom the perspective of the server 110 performing the method 700.However, some or all of the steps may be performed by other entities orcomponents. In addition, some embodiments may perform the steps inparallel, perform the steps in different orders, or perform differentsteps.

In the embodiment shown in FIG. 7 , the method 700 begins with theserver 110 receiving 710 a request to synchronize data to a data tableusing email. For example, the server 110 stores a database including thedata table, and a user that created the database sends the request tothe server 110 using a client device 140.

The server 110 generates 720 a table email address for the data table.The table email address is an email address for an email account managedby or accessible by the server 110. Each data table configured for emailsynchronization may have a unique email address. Depending upon theembodiment, the table email address may include information relevant toa sender of the request or the data table. In one embodiment, the tableemail address includes a user-provided string (e.g., a word or phrase),a hyphen, and an alphanumeric string (e.g., a data table identifier).Depending upon the embodiment, the user-provided string may be received,by the server 110, from a client device 140, or the server 110 maygenerate the user-provided string based on one or more stringsassociated with the data table, such as a name of the data table. Forexample, the data table may be titled “Orders” and the sender of therequest may be a business called “Example Service Provider.” The tableemail address may therefore be, for example,“example-service-provider-orders@exampleaddress.com.” In an embodiment,the table email address includes an identifier generated by the server,such as an alphanumeric string. For example, the table email address maybe “8jhf94aw3n@exampleaddress.com.” In some embodiments, the table emailaddress includes information relevant to the sender of the request orthe data table, and also an identifier generated by the server. Forexample, the email address may be “example-service-provider-orders-8jhf94aw3n@exampleaddress.com.”

The server 110 receives 730 an email addressed to the table emailaddress and including a data file with one or more records andrespective record identifiers. The record identifiers may be features ofthe respective records, e.g., for each record, a particular attribute.In an embodiment, the attribute that is the record identifier of therecords in the data file is a primary key in a database. In anembodiment, the server 110 identifies a record identifier as invalidunless each record has a different record identifier, such that no tworecords share a record identifier. In one embodiment, the data file is acomma-separated values (CSV) file. In alternative embodiments, the datafile may be a compressed CSV file (e.g., a ZIP file of a CSV file), atab-separated value (TSV) file, a JavaScript Object Notation (JSON)file, an Extensible Markup Language (XML) file, or a MICROSOFT EXCELfile. It is noted that alternative data file types than those disclosedherein may be employed without departing from the principles andtechniques described herein.

The email may be received from a client device 140. In an embodiment,the server 110 only interacts with emails from a preset list of emailaddresses, e.g., a list set by an administrator of the data table. Forexample, an administrator of a business may configure the server 110such that only email addresses of users associated with (e.g., employedby) the business are on the list.

The server 110 maps 740 the one or more records of the data file to thedata table using the respective record identifiers. Each record in thedata table has a record identifier and each record in the data file hasa record identifier. The server 110 matches records in the data filewith records in the data table that have identical record identifiers.

The server 110 updates 750 the data table using the mapped one or morerecords. For example, the server 110 changes the data of each matchedrecord in the data table with the data of the respective record from thedata file. If a record in the data file does not match to a record inthe data table, the server 110 adds the record to the data table as anew entry. In an embodiment, the new entry has a data type matching thedata type of the record in the data file. In some embodiments, one ormore new entries are converted to a different data type, e.g., accordingto a data type map of data file data types to data table data types.

If the data table includes a record that is not matched to a record inthe data file, depending upon the embodiment, the server 110 eitherremoves the record from the data table or leaves it unchanged. Whetherthe record is removed (e.g., deleted) or left unchanged may be set by auser (e.g., via an instruction received from a client device 145), inone embodiment. In an embodiment, the user can manually remove a recordfrom the data table. Depending upon the embodiment, the user may be ableto manually add or modify records in the data table.

In an embodiment, the server 110 additionally or alternatively updates async history of the data table. The sync history is one or more datafiles that tracks the data of each record in the data table after eachsynchronization to the data table. For example, when the data table iscreated, it includes no records. After a first synchronization of datato the data table (e.g., via data synchronization), the sync historyincludes an initial set of records. After a second synchronization, thesync history includes the initial set of records and also an updated setof records corresponding to the second synchronization. Data from eachsynchronization is maintained in the sync history on a per-record basisaccording to the respective record identifier. As a particular example,at the first synchronization, a particular record may have the value“55” and a record identifier of “a8dd83.” At the second synchronization,the particular record may have the value “94” and the record identifier“a8dd83.” The sync history indicates that the particular record,identified by the record identifier of “a8dd83,” had the value “55”after the first synchronization and the value of “94” after the secondsynchronization. In this manner, changes to the data table, orparticular records, can be tracked over time.

In an embodiment, the server 110 can duplicate the data table. Forexample, the server 110 may do so responsive to receiving a request froma client 145 to do so. The duplicate of the data table may beasynchronous, e.g., it is not updated during subsequent synchronizationsto the data table.

Email Synchronization Setup User Interface

FIG. 8 illustrates a user interface for email synchronization to adatabase table, according to one embodiment. The user interface isdisplayed upon loading a data file from an email into the server 110, inone embodiment. Depending upon the embodiment, the user interface may beused during creation of a base from a data file, or upon synchronizationof data to a base from a data file received in an email.

The user interface includes an edit table graphical element 802 withinwhich is a table preview graphical element 804. User input to the edittable graphical element 802 can alter how the server 110 performs theemail synchronization. The table preview graphical element 804 is arepresentation of the data in the data file from an email to bysynchronized during an email synchronization process. Each field of thetable preview graphical element 804 contains an edit field graphicalelement 806. User input to the edit field graphical element 806, such asa select action using an input device, opens a menu of edit options. Theedit options can include changing the field name and configuring thefield type.

The user interface also includes a record identifier graphical element808 that has a selection dropdown graphical element 812 in someembodiments. The record identifier graphical element 808 is a box, sucha text box, to which user input may be applied to indicate a field inthe data file to be used by the server 110 as the record identifier. Theselection dropdown graphical element 812 can be selected by user inputand responsively presents a dropdown menu of fields from which the usercan select a record identifier. The fields in the dropdown menu may beall fields in the data, or may be a subset of the fields, e.g., fieldsfor which the server 110 has determined each record in the received datais different from all other records in the received data.

The user interface includes a create graphical element 814, in someembodiments. Upon user input to the create graphical element 814, theserver 110 creates the table as configured in the edit table graphicalelement 802, or applies the received data to an existing table accordingto the data as configured in the edit table graphical element 802. Theserver 110 may use the record identifier specified by the recordidentifier graphical element 808 as the record identifier, in someembodiments.

Email Synchronization Error User Interface

FIG. 9 illustrates a user interface to visualize a database error,according to one embodiment. The user interface includes a notification902 that a synchronization failed, as well as a description 904 of thespecific failure that occurred. The user interface also includes arepresentation of a portion 906 of the data table. The portion 906includes a representation of the error, useful in identifying theproblem that caused the error. For example, in the figure, row sixincludes the characters “

” instead of a product name, and rows one and six share a transactionID, which correspond to the two errors in the description 904. In anembodiment, when the server 110 detects an error, it generates thenotification 902, the description 904, and portion 906 and sends themfor display to a client device 140. In this manner, the server 110 canvisually represent the error, better enabling its correction.

Computing System Architecture

FIG. 10 is a block diagram illustrating an example computer 1000suitable for use as the server 110 or a client device 140. The examplecomputer 1000 includes at least one processor 1002 coupled to a chipset1004. The chipset 1004 includes a memory controller hub 1020 and aninput/output (I/O) controller hub 1022. A memory 1006 and a graphicsadapter 1012 are coupled to the memory controller hub 1020, and adisplay 1018 is coupled to the graphics adapter 1012. A storage device1008, keyboard 1010, pointing device 1014, and network adapter 1016 arecoupled to the I/O controller hub 1022. Other embodiments of thecomputer 1000 have different architectures.

In the embodiment shown in FIG. 10 , the storage device 1008 is anon-transitory computer-readable storage medium such as a hard drive,compact disk read-only memory (CD-ROM), DVD, or a solid-state memorydevice. The memory 1006 holds instructions and data used by theprocessor 1002. The pointing device 1014 is a mouse, track ball,touchscreen, or other type of pointing device, and is used incombination with the keyboard 1010 (which may be an on-screen keyboard)to input data into the computer system 1000. The graphics adapter 1012displays images and other information on the display 1018. The networkadapter 1016 couples the computer system 1000 to one or more computernetworks.

The types of computers used by the entities of FIGS. 1 through 4 canvary depending upon the embodiment and the processing power required bythe entity. For example, the server 110 might include a distributeddatabase system comprising multiple blade servers working together toprovide the functionality described. Furthermore, the computers can lacksome of the components described above, such as keyboards 1010, graphicsadapters 1012, and displays

Additional Considerations

In various embodiments, aggregated synchronization can also be referredto as multisource synchronization.

Some portions of above description describe the embodiments in terms ofalgorithmic processes or operations. These algorithmic descriptions andrepresentations are commonly used by those skilled in the computing artsto convey the substance of their work effectively to others skilled inthe art. These operations, while described functionally,computationally, or logically, are understood to be implemented bycomputer programs comprising instructions for execution by a processoror equivalent electrical circuits, microcode, or the like. Furthermore,it has also proven convenient at times, to refer to these arrangementsof functional operations as modules, without loss of generality.

As used herein, any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment. Similarly, use of “a” or “an” preceding an element orcomponent is done merely for convenience. This description should beunderstood to mean that one or more of the elements or components arepresent unless it is obvious that it is meant otherwise.

Where values are described as “approximate” or “substantially” (or theirderivatives), such values should be construed as accurate +/−10% unlessanother meaning is apparent from the context. From example,“approximately ten” should be understood to mean “in a range from nineto eleven.”

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and a process for providing partial synchronization of databasetables. Thus, while particular embodiments and applications have beenillustrated and described, it is to be understood that the describedsubject matter is not limited to the precise construction and componentsdisclosed. The scope of protection should be limited only by thefollowing claims.

What is claimed is:
 1. A computer-implemented method for emailsynchronization of a data table, the computer-implemented methodcomprising: receiving, by a server comprising a processor, a request tosynchronize data to a data table using an email; generating, by theserver, a table email address for the data table, wherein the tableemail address is a new email address associated with the data table;receiving, by the server, an email addressed to the table email address,wherein the email comprises a data file including one or more records,each record of the one or more records comprising a respective recordidentifier; mapping, by the server, the one or more records to the datatable using the respective record identifiers; and updating, by theserver, the data table using the mapped one or more records.
 2. Thecomputer-implemented method of claim 1, wherein the data file is acomma-separated value file.
 3. The computer-implemented method of claim1, further comprising: receiving, by the server, a request tosynchronize data to the data table from a second data source; andsynchronizing, by the server, data from the second data source to thedata table.
 4. The computer-implemented method of claim 1, furthercomprising: receiving, by the server, a request view a sync history ofthe data table; and sending to a client device for display, by theserver, the sync history of the data table, wherein the sync history ofthe data table comprises, for each record identifier in the data table,a value of the respective record after each historic synchronization tothe data table.
 5. The computer-implemented method of claim 1, whereineach respective record identifier is an attribute of the one or morerecords in the data file.
 6. The computer-implemented method of claim 1,further comprising: receiving, by the server, a record identifierselection, wherein the record identifier selection determines, for eachof the one or more records, the respective record identifier.
 7. Thecomputer-implemented method of claim 1, further comprising: determining,by the server, a record identifier selection, wherein the recordidentifier selection determines, for each of the one or more records,the respective record identifier.
 8. A non-transitory computer-readablestorage medium storing computer program instructions executable by oneor more processors, the instructions comprising instructions to:receive, by a server comprising a processor, a request to synchronizedata to a data table using an email; generate, by the server, a tableemail address for the data table, wherein the table email address is anew email address associated with the data table; receive, by theserver, an email addressed to the table email address, wherein the emailcomprises a data file including one or more records, each record of theone or more records comprising a respective record identifier; map, bythe server, the one or more records to the data table using therespective record identifiers; and update, by the server, the data tableusing the mapped one or more records.
 9. The non-transitorycomputer-readable storage medium of claim 8, wherein the data file is acomma-separated value file.
 10. The non-transitory computer-readablestorage medium of claim 8, the instructions comprising instructions to:receive, by the server, a request to synchronize data to the data tablefrom a second data source; and synchronize, by the server, data from thesecond data source to the data table.
 11. The non-transitorycomputer-readable storage medium of claim 8, the instructions comprisinginstructions to: receive, by the server, a request view a sync historyof the data table; and send to a client device for display, by theserver, the sync history of the data table, wherein the sync history ofthe data table comprises, for each record identifier in the data table,a value of the respective record after each historic synchronization tothe data table.
 12. The non-transitory computer-readable storage mediumof claim 8, wherein each respective record identifier is an attribute ofthe one or more records in the data file.
 13. The non-transitorycomputer-readable storage medium of claim 8, the instructions comprisinginstructions to: receive, by the server, a record identifier selection,wherein the record identifier selection determines, for each of the oneor more records, the respective record identifier.
 14. Thenon-transitory computer-readable storage medium of claim 8, theinstructions comprising instructions to: determine, by the server, arecord identifier selection, wherein the record identifier selectiondetermines, for each of the one or more records, the respective recordidentifier.
 15. A system, the system comprising: one or more processors;and a non-transitory computer-readable storage medium storing computerprogram instructions executable by the one or more processors, theinstructions comprising instructions to: receive, by a server comprisinga processor, a request to synchronize data to a data table using anemail; generate, by the server, a table email address for the datatable, wherein the table email address is a new email address associatedwith the data table; receive, by the server, an email addressed to thetable email address, wherein the email comprises a data file includingone or more records, each record of the one or more records comprising arespective record identifier; map, by the server, the one or morerecords to the data table using the respective record identifiers; andupdate, by the server, the data table using the mapped one or morerecords.
 16. The system of claim 15, the instructions comprisinginstructions to: receive, by the server, a request to synchronize datato the data table from a second data source; and synchronize, by theserver, data from the second data source to the data table.
 17. Thesystem of claim 15, the instructions comprising instructions to:receive, by the server, a request view a sync history of the data table;and send to a client device for display, by the server, the sync historyof the data table, wherein the sync history of the data table comprises,for each record identifier in the data table, a value of the respectiverecord after each historic synchronization to the data table.
 18. Thesystem of claim 15, wherein each respective record identifier is anattribute of the one or more records in the data file.
 19. The system ofclaim 15, the instructions comprising instructions to: receive, by theserver, a record identifier selection, wherein the record identifierselection determines, for each of the one or more records, therespective record identifier.
 20. The system of claim 15, theinstructions comprising instructions to: determine, by the server, arecord identifier selection, wherein the record identifier selectiondetermines, for each of the one or more records, the respective recordidentifier.